AT the company I work for we have to provide remote access to two mapped drives via VPN. The problem began when we upgraded from Server 2003, to server 2008 R2. In S2003, we used a standard VPN for access to the Users Windows 7 client systems and never had a problem. The SQL software vendor specified that we maintain a "Named Server" mapping. For many years, this worked fine. When we upgraded to server 2008 R2, it seems the rules changed every day. Sometimes for some people in some places, the VPN has to use the IP which I personally believe is the right way. But occasionally, for some the VPN wont work unless I use the old "named server" (ie:win-abc123def4g). By now, I think I have tried it all. I have spoken to several MS techs and gotten all kinds of different solutions. Sometimes, some of them work. Other times, not. In addition, regardless of how the VPN connects, sometimes the drives have to be mapped to the server by the name other times by the IP. I have tried setting various permissions and other things but it seems that the issues is the actual "addressing" of the server. If IPV-4 is already moving to IPV6 due to a lack of addresses, I dont see where there is room for a "named server" instance where the "name" is anything you choose to use. Unless you also have a Domain controller or in some way tie this name back to the outward facing IP on the NIC, how are people EVER able to connect using a name that has no relation to the IP being broadcast by the server? If there is a way, why does it work in only a few places for a few people and not for all? And why doesn't it always work as a name for the ones who get it by name occasionally? Sometimes even those people have to resort to using the IP. Let me add that we tried removing the router and firewall so that the NIC itself was directly connected to the static IP off the T1. This still solved nothing. Anyone with any ideas would be greatly appreciated. I should add that we do not have a WINS server nor is this system on a Domain, just a Workgroup. Additonally, the VPN's are currently only using PPTP and the users require the gateway to be provided by their local network while connected. I guess a "Semi-Private" personal network would be a more appropriate name. V(sp)N?

1. Perhaps there are old data in DNS cache 2. What nslookup say? Regards Milos

Hi , As this issue is related to Windows Server 2008 R2, in order to get the answer effectively, it is recommended to post a new question in the Network Infrastructure Servers for further discussion. The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.Tracy Cai TechNet Community Support